Hi, Is it possible to link the IDs of two separate documents such that if document A has objects with IDs let's say a, b,c and the document B has objects with IDs d and e and when I change the ID b in document A to c, the updated IDs in document A become a,c,d and the IDs in document B become e, f? Is it possible to do so in DOORS? Many thanks in advance for your kind attention and support, Melih Melih_ - Thu Aug 28 05:40:28 EDT 2014 |
Re: Linking different document IDs Object IDs are created automatically by DOORS and can never be changed. This is one of the strengths of the tool. If, as I think you are trying to keep your IDs in some sort of numerical order so they look tidy then this is a big mistake. Let DOORS handle the IDs and do not attribute any meaning to the numbering. Tony |
Re: Linking different document IDs Tony_Goodman - Thu Aug 28 09:54:38 EDT 2014 Object IDs are created automatically by DOORS and can never be changed. This is one of the strengths of the tool. If, as I think you are trying to keep your IDs in some sort of numerical order so they look tidy then this is a big mistake. Let DOORS handle the IDs and do not attribute any meaning to the numbering. Tony Hi Tony, Many thanks for your very kind and prompt reply. Equally, your advice is very much appreciated. Many thanks once more for your time and attention. Cheers, Melih
|
Re: Linking different document IDs I think you want some sort of "Object Ordering" string or int attribute. Then you can modify the contents as you want. -Louie |
Re: Linking different document IDs Also, why would you want to? If folks have refererence the second object in A as "e"; these folks will get confused if it becomes "f" and some other object becomes "e". More importantly, any documented references are not invalid. |
Re: Linking different document IDs llandale - Fri Aug 29 14:03:10 EDT 2014 Also, why would you want to? If folks have refererence the second object in A as "e"; these folks will get confused if it becomes "f" and some other object becomes "e". More importantly, any documented references are not invalid. Hi Louie, Firstly many thanks for your kind reply and for the time that you spared answering my inquiry. The reason why I wanted to do it, because actually these are not customer driven requirements but rather pretty static specs. However from time to time we might need to modify these specs stored in DOORS slightly. Thus each time when we want to migrate these requirements for a different project we do not want to change the IDs again one by one manual. However what I understood from Tony's reply that it was not possible to do so in Doors. Many thanks once more for your kind replies and wish you an excellent week, Melih
|
Re: Linking different document IDs Melih_ - Mon Sep 01 04:39:50 EDT 2014 Hi Louie, Firstly many thanks for your kind reply and for the time that you spared answering my inquiry. The reason why I wanted to do it, because actually these are not customer driven requirements but rather pretty static specs. However from time to time we might need to modify these specs stored in DOORS slightly. Thus each time when we want to migrate these requirements for a different project we do not want to change the IDs again one by one manual. However what I understood from Tony's reply that it was not possible to do so in Doors. Many thanks once more for your kind replies and wish you an excellent week, Melih
You have the option of creating an Object Ordering attribute as Louie suggested. Would it word for you to use this as the obvious, large text, identification of your requirement, but then to include the real Object Identifier with the requirement in a de-emphasised text. This would give your users the outlining they expect, but also give you (and them) traceability between versions by using the unique identifiers. What you are describing seems to me to be almost like a heading numbering, which is transient, and structure dependent. There is a place for this type of information, but there is huge value to including the unique identifiers as well as Tony said. |
Re: Linking different document IDs HazelWoodcock - Tue Sep 02 07:52:07 EDT 2014 You have the option of creating an Object Ordering attribute as Louie suggested. Would it word for you to use this as the obvious, large text, identification of your requirement, but then to include the real Object Identifier with the requirement in a de-emphasised text. This would give your users the outlining they expect, but also give you (and them) traceability between versions by using the unique identifiers. What you are describing seems to me to be almost like a heading numbering, which is transient, and structure dependent. There is a place for this type of information, but there is huge value to including the unique identifiers as well as Tony said. Hi Hazel, Many thanks for your detailed and kind response. Eventually based on your inputs, I had a brief discussion and we will be assigning unique IDs against the requirements as it will enable us to establish full traceability across multiple documents. Even though we can manage to do so, it might be dangerous if the other documents like dFMEA, safety, etc. are not updated accordingly. Besides if people dwell in complacency, highly likely that they might not be attentive enough of the maintenance of these documents. Many thanks once more for all your valuable inputs. With my kindest regards, Melih |